The WSDL transport provider can be used to for invoking remote web services by obtaining the service WSDL. Mule will create a dynamic proxy for the service then invoke it.

The javadoc for this provider can be found here.

WSDL Connector Properties

There are no properties to set on a WSDL connector.

WSDL Endpoints

The WSDL endpoint works in much the same way as the other SOAP endpoints such as Axis, Glue or XFire. You must provide the full URL to the WSDL of the service to invoke and you must also supply a 'method' parameter which tells Mule which operation to invoke on the service -

wsdl:http://www.webservicex.net/stockquote.asmx?WSDL&method=GetQuote

The WSDL URL is pre-pended with wsdl:. Behand the scenes Mule will check you class path to see if there is a WSDL provider that it can use to create a client proxy from the WSDL. Mule supports the Axis and XFire methods. If you want to use a specific one you can specify which on the URL i.e.

wsdl-xfire:http://www.webservicex.net/stockquote.asmx?WSDL&method=GetQuote

or

wsdl-axis:http://www.webservicex.net/stockquote.asmx?WSDL&method=GetQuote

The javadoc for the Xfire WSDL dispatcher can be found here.

The javadoc for the AxisWSDL dispatcher can be found here.

Issue with Axis Sometimes the Axis WSDL generation will not work (Incorrect namespaces are used) So you might want to experiment with each one. We have had no problems with the XFire WSDL generation so far

Transformers

There are no specific transformers to set on WSDL endpoints.